dur is an integer from 1 through 1440.
This command sets the timeout duration to maintain the IMSI White List received from HMS/BAC during HNB registration procedure in HNB-GW service for the configured dur in minutes after de-registration of all referenced HNBs from HNB-GW node and then purge the database.
associate gtpu-service svc_name
svc_name ise an alphanumeric string of 1 through 63 characters.
Important: Another GTP-U service can be used to bind the HNB-GW service towards the Core Network and can be configured in HNB-PS Configuration mode. For more information on GTP-U service configuration, refer GTP-U Service Configuration Mode Commands.Following command associates GTP-U service named gtpu-hnb1 with specific HNB-GW service towards Home-NodeB side.
associate rtp pool pool_name
pool_name is an alphanumeric string of 1 through 31 characters.
Important: For IP pool (RTP pool) configuration, refer ip pool command in Context Configuration Mode Commands chapter.
Important: This command must be used to provide IP address for mapping of RTP streams on Iuh interface between HNB and HNB-GW.Following command associates RTP pool named rtp_1 with HNB-GW service for RTP stream end point from Home-NodeB:
Important: UE-Reg/CS-Call/PS-Call requests (both existing and future) is allowed from already registered Open HNBs even after operator has disabled the Open Access support. No new Open HNB registration is allowed once operator disables the Open Access support.open max-registered-ue reg_ue
reg_ue defines the maximum number of UEs that can register from an Open HNB as an integer from 1 through 32.
This command enable Open Access mode support to allow the UEs that can register from an Open HNB. If a UE tries to register from an Open HNB with an HNB-GW service instance, which is already reached to the limit configured through max-registered-ue reg_ue the HNB-GW sends HNB-Registration-Reject message with “ue not allowed in this hnb” cause.
Important: If Operator has reduced the maximum number of UEs allowed per Open HNB during the session, this will not have any effect on already registered UEs/CS-Calls/PS-Calls even if previously configured reg_ue is beyond the newly configured reg_ue value. Limits is respected while handling new requests.Use this keyword to place the configuration in pass-through mode (no marking of DSCP). Use of this keyword is allowed even when there is no previous DSCP parameter set.
Important: In this configuration the no keyword does not disable or remove a previous configuration.sctp payload all dscp_code
|
•
|
GTP-U: cs1
|
|
•
|
RTCP: ef
|
|
•
|
RTP: af41
|
following type of DSCP codes dscp_code are supported over IuH interface:
|
•
|
af11: Marks traffic as Assured Forwarding 11 PHB (high throughput data)
|
|
•
|
af12: Marks traffic as Assured Forwarding 12 PHB (high throughput data)
|
|
•
|
af13: Marks traffic as Assured Forwarding 13 PHB (high throughput data)
|
|
•
|
af21: Marks traffic as Assured Forwarding 21 PHB (low latency data)
|
|
•
|
af22: Marks traffic as Assured Forwarding 22 PHB (low latency data)
|
|
•
|
af23: Marks traffic as Assured Forwarding 23 PHB (low latency data)
|
|
•
|
af31: Marks traffic as Assured Forwarding 31 PHB (multimedia streaming)
|
|
•
|
af32: Marks traffic as Assured Forwarding 32 PHB (multimedia streaming)
|
|
•
|
af33: Marks traffic as Assured Forwarding 33 PHB (multimedia streaming)
|
|
•
|
af41: Marks traffic as Assured Forwarding 41 PHB (multimedia conferencing). This is the default DSCP code for RTP payloads in UDP protocol.
|
|
•
|
af42: Marks traffic as Assured Forwarding 42 PHB (multimedia conferencing)
|
|
•
|
af43: Marks traffic as Assured Forwarding 43 PHB (multimedia conferencing)
|
|
•
|
cs1: Marks traffic with Class Selector 1 (low priority data). This is the default DSCP code for GTP-U payloads in UDP protocol.
|
|
•
|
cs2: Marks traffic with Class Selector 2 (OAM)
|
|
•
|
cs3: Marks traffic with Class Selector 3 (broadcast video)
|
|
•
|
cs4: Marks traffic with Class Selector 4 (real-time interactive)
|
|
•
|
cs5: Marks traffic with Class Selector 5 (signaling). This is the default DSCP code for all SCTP payloads.
|
|
•
|
cs6: Marks traffic with Class Selector 6 (network control)
|
|
•
|
df : Marks traffic as Default Forwarding (best effort: DSCP = 0)
|
|
•
|
ef: Marks traffic as Expedited Forwarding PHB (telephony). This is the default DSCP code for RTCP payloads in UDP protocol.
|
This command adds DSCP marking on egress traffic going towards CN (CS/PS). To make the configuration pass-through mode or not marking DSCP at all in the packets, no variant of command is used. Use of no is allowed even when there is no previous DSCP configuration done.
Important: By default this command is Disabled.
Important: When DSCP configuration is not specified, the system works in pass-through mode and DSCP values in the ingress (from CN) and egress (to HNB) data packets remain unchanged. Multiple traffic classes can share the same code point value.Use this keyword to set the configuration in pass-through mode. Use of this keyword is allowed even when there is no previous DSCP parameter set.
Important: In this configuration the no keyword does not disable/remove a previous configuration.sctp payload all dscp_code
|
•
|
GTP-U: cs1
|
|
•
|
RTCP: ef
|
|
•
|
RTP: af41
|
following type of DSCP codes dscp_code are supported over IuH interface:
|
•
|
af11: Marks traffic as Assured Forwarding 11 PHB (high throughput data)
|
|
•
|
af12: Marks traffic as Assured Forwarding 12 PHB (high throughput data)
|
|
•
|
af13: Marks traffic as Assured Forwarding 13 PHB (high throughput data)
|
|
•
|
af21: Marks traffic as Assured Forwarding 21 PHB (low latency data)
|
|
•
|
af22: Marks traffic as Assured Forwarding 22 PHB (low latency data)
|
|
•
|
af23: Marks traffic as Assured Forwarding 23 PHB (low latency data)
|
|
•
|
af31: Marks traffic as Assured Forwarding 31 PHB (multimedia streaming)
|
|
•
|
af32: Marks traffic as Assured Forwarding 32 PHB (multimedia streaming)
|
|
•
|
af33: Marks traffic as Assured Forwarding 33 PHB (multimedia streaming)
|
|
•
|
af41: Marks traffic as Assured Forwarding 41 PHB (multimedia conferencing). This is the default DSCP code for RTP payloads in UDP protocol.
|
|
•
|
af42: Marks traffic as Assured Forwarding 42 PHB (multimedia conferencing)
|
|
•
|
af43: Marks traffic as Assured Forwarding 43 PHB (multimedia conferencing)
|
|
•
|
cs1: Marks traffic with Class Selector 1 (low priority data). This is the default DSCP code for GTP-U payloads in UDP protocol.
|
|
•
|
cs2: Marks traffic with Class Selector 2 (OAM)
|
|
•
|
cs3: Marks traffic with Class Selector 3 (broadcast video)
|
|
•
|
cs4: Marks traffic with Class Selector 4 (real-time interactive)
|
|
•
|
cs5: Marks traffic with Class Selector 5 (signaling). This is the default DSCP code for all SCTP payloads.
|
|
•
|
cs6: Marks traffic with Class Selector 6 (network control)
|
|
•
|
df : Marks traffic as Default Forwarding (best effort: DSCP = 0)
|
|
•
|
ef: Marks traffic as Expedited Forwarding PHB (telephony). This is the default DSCP code for RTCP payloads in UDP protocol.
|
This command adds DSCP marking on egress traffic going towards HNB. To make the configuration pass-through mode or not marking DSCP at all in the packets, no variant of command is used. Use of no is allowed even when there is no previous DSCP configuration done.
Important: By default this command is Disabled.
Important: When DSCP configuration is not specified, system works in pass-through mode and DSCP value in the ingress (from CN) and egress (to HNB) control and data packets remain unchanged. Multiple traffic classes can share the same code point value.always: Sets the system to ALWAYS page the open HNBs irrespective of paging-area IE is received in paging messages.
never: Sets the system to NEVER page any open HNB.
only-if-with-paging-area: Sets the system to page the open HNBs only when paging-area IE is received in paging messages.
always: Sets the system to ALWAYS page the open HNBs from where the UE is registered. If the UE is not registered then it pages the open HNBs irrespective of paging-area IE is received in paging messages.
never: Sets the system to page the open HNBs from where the UE is registered. If the UE is not registered then it NEVER pages any open HNB.
only-if-with-paging-area: Sets the system to ALWAYS page the open HNBs from where the UE is registered. If the UE is not registered then it pages the open HNBs only when paging-area IE is received in paging messages.
Caution: Removing the PLMN-ID is a disruptive operation; the HNB-GW service will be re-started.mcc mcc_num
mnc mnc_num
Caution: Changing or removing the PLMN-ID is a disruptive operation; the HNB-GW service will be re-started.The following command configures the radio network PLMN identifier with MCC value as 102 and MNC value as 20 for an HNB-GW service:
ranap reset {ack-timeout timer_value | guard-timeout g_timer | hnbgw-initiated | max-retransmissions retries}
ack-timeout timer_value
timer_value is an integer value from 5 through 10. Default: 10
guard-timeout g_timer_value
g_timer_value is an integer value from 5 through 10. Default: 10
max-retransmission retries
retries is an integer value from 0 through 2. When 0 is used retransmission is disabled. Default: 1
interval dur
Important: The same interval is applicable for all kinds of RTCP packets/ reports across all sessions on an HNB-GW service.The following command configures the RTCP report generation interval to 15 seconds on an HNB-GW service for RTP stream:
default sctp {alpha-rto | beta-rto | checksum-type | cookie-life | max-retx [ init | path | assoc] | mtu-size [start | min | max ] | rto { initial | min | max} | sack-frequency | sack-period | max-in-strms | max-out-strms }
|
•
|
alpha-rto: 5 seconds
|
|
•
|
beta-rto: 10 seconds
|
|
•
|
checksum-type: CRC32
|
|
•
|
cookie-life: 600 ms
|
|
•
|
max-retx init: 5 retries
|
|
•
|
max-retx path: 5 retries
|
|
•
|
max-retx assoc: 10 retries
|
|
•
|
mtu-size min: 508 Bytes
|
|
•
|
mtu-size max: 1500 Bytes
|
|
•
|
mtu-size start: 508 Bytes
|
|
•
|
rto initial: 30 seconds
|
|
•
|
rto min: 10 seconds
|
|
•
|
rto max: 600 seconds
|
|
•
|
|
•
|
sack-period: 2 ms
|
|
•
|
max-in-strms: 4
|
|
•
|
alpha-rto alpha_rto_dur
beta-rto beta_rto_dur
adler32: Specifies the SCTP association to use Adler32 checksum algorithm for packet validation. By default this is disabled.
crc32: Specifies the SCTP association to use 32-bit cyclic redundancy check (CRC) algorithm for packet validation. By default this is enabled.
cookie-life cookie_life
init: Sets the maximum attempts allowed after T1-init timer expires. If the T1-init timer expires then the HNB-GW retransmits INIT chunk and re-start the T1-init timer without changing state. This is repeated up to the configured times with this configuration. After that, the HNB-GW aborts the initialization process. Default number of attempts max_retry for this state is 5.
path: Sets the maximum attempts allowed after T3-rtx timer expires. Each time the T3-rtx timer expires on any address, or when a HEARTBEAT sent to an idle address is not acknowledged within a RTO, the error counter of that destination address incremented. When the value in the error counter exceeds this protocol parameter of that HNB address, the HNB-GW marks the destination transport address as inactive. Default number of attempts max_retry for this state is 5.
assoc: Sets the maximum number of consecutive retransmissions to its peer is allowed. If the value of this counter exceeds the limit configured with this keyword the HNB-GW considers the peer HNB unreachable and stop transmitting any more data to it. The SCTP association is automatically closed when the peer endpoint becomes unreachable. Default number of attempts max_retry for this state is 10.
max_retry is an integer from 1 through 255.
min: Sets the minimum size of MTU for SCTP association between HNB and HNB-GW. Default minimum MTU size mtu_byte is 508 Bytes.
max: Sets the maximum size of MTU for SCTP association between HNB and HNB-GW. Default maximum MTU size mtu_byte is 1500 Bytes.
start: Sets the size of MTU for SCTP association at the start of session between HNB and HNB-GW. Default MTU size mtu_byte at initial sate is 508 Bytes.
mtu_byte is an integer from 508 to 65535.
initial ini_rto_dur: Sets the initial retransmission timeout duration (in seocnds) for SCTP association between HNB and HNB-GW as an integer from 1 through 1200. Default: 30.
min min_rto_dur: Sets the minimal retransmission timeout duration (in seconds) for SCTP association between HNB and HNB-GW as an integer from 1 through 50. Default: 10
max max_rto_dur: Sets the maximum retransmission timeout duration (in secinds) for SCTP association between HNB and HNB-GW as an integer from 5 through 1200. Default: 600.
sack-frequency sack_frq
sack_frq is the frequency after which SACK chunk is sent to HNB specified as an integer from 1 through 5. Default: 2
sack-period sack_dur
sack_dur is an integer from 0 through 5. A “zero” value disables the parameter.
max-in-strms in_strms
max-out-strms out_strms
The following command sets the SCTP COOKIE life to 600 milliseconds on HNB-GW for the SCTP association:
address address
port port_num
The following command sets the SCTP port number 999 on HNB-GW to listen from Home-NodeB over Iuh interface:
The following command sets the SCTP address 10.2.3.4 of HNB-GW to use with Home-NodeB over Iuh interface:
dur is an integer from 5 through 30. Default: 10
The following command sets the SCTP connection timeout duration to 15 second on HNB-GW after expiry of which the SCTP association is removed:
dur is an integer from 1 through 300. Default: 30
The following command sets the SCTP HEARTBEAT timeout duration to 15 second on HNB-GW after expiry of which the HNB-GW retransmits the HEARTBAT chunk to HNB over SCTP association:
security-gateway aaa authentication { first-phase | second-phase } context ctx_name aaa-group aaa_grp
first-phase: Specifies the parameters to be used for first phase of authentication while using SeGW functionality in an HNB-GW service. This associates the AAA parameters through AAA server group association with in it.
second-phase: Specifies the parameters to be used for second phase of authentication while using SeGW functionality in an HNB-GW service. This associates the AAA parameters through AAA server group association with in it.
context ctx_name: Specifies the name of the context to be used for first/second or both phases of authentication.
aaa-group aaa_grp: Specifies the name of the AAA server group configured via Context Configuration mode with AAA parameters that will be used for first/second or both phases of authentication.
Important: For more information on AAA server groups, refer AAA Server Group Configuration Mode Commands.
Caution: This is a critical configuration and need to be configured carefully when Security Gateway (SeGW) functionality required on HNB-GW service.The following command associates an AAA server group named sec_gw_grp1 with HNB-GW service to use specific AAA authentication parameters in first phase of authentication and another AAA server group named sec_gw_grp2 to use different AAA authentication parameter in second phase of authentication. Both AAA server groups are configured in same context named SeGW_ctx1:
bind address address
crypto-template cryp_name
cryp_name specifies the name of the pre-configured Crypto-map template which is configured in Crypto-Map Template Configuration mode and associated with the HNB-GW service to create an IPSec tunnel with a Home-NodeB during HNB-GW discovery procedure over an Iuh interface.
context ctx_name
Caution: This is a critical configuration. The HNB-GW service cannot be started without this configuration. Any change to this configuration would lead to restarting the HNB-GW service and removing or disabling this configuration stops the HNB-GW service.The following command binds the logical IP interface with the address of 10.2.3.4 to the HNB-GW service using existing IPsec Crypto-Map template crypto1 to establish IPSec tunnel with Home-NodeB:
The following command sets the system to strip the MAC address from user name received from user MS:
tnnsf-timer dur
tnnsf-timer dur
Whenever the MSC sends the paging request with IMSI, the HNB-GW stores the Global_CN_ID of the node which issued the paging request message for the given IMSI and HNB-GW starts the tnnsf-timer. HNBGW stores the mapping of IMSI to Global_CN_ID until the tnnsf-timer expires
The following command sets the NNSF timer value to 30 seconds in an HNB-GW service instance:
dur is an integer from 60 through 300. Default: 120
The following command sets the UE registration timeout duration to 150 second on HNB-GW after expiry of which the UE is de-registered:
